Copyright ã1995 by NeXT Computer, Inc.  All Rights Reserved.

DBFormatterValidation
(informal protocol)

Category Of:	Object

Declared In:	dbkit/tableProtocols.h

Category Description

This informal protocol  is one of the mechanisms the Database Kit uses to place objects into the database.  If a class is associated with a property and it implements this method, this method will be called when the kit tries to store the object into the database.

Method Types

Notifications by identifiers 	- formatterDidChangeValueFor::to:sender:
- formatterWillChangeValueFor::sender:
- formatterWillChangeValueFor::to:sender:

Notification by position 	- formatterDidChangeValueFor:at:to:sender:
- formatterWillChangeValueFor:at:sender:
- formatterWillChangeValueFor:at:to:sender:

Instance Methods

formatterDidChangeValueFor::sender:

- formatterDidChangeValueFor:rowIdentifier 
:columnIdentifer 
sender:sender

Notification that may be sent when the formatter has changed the value in a field.  The field that changed is identified by its rowIdentifier and its columnIdentifier (for the situation in which both rows and columns are static).

The argument sender is the sender of the message (usually a formatter).  Returns self.

formatterDidChangeValueFor::to:sender:

- formatterDidChangeValueFor:rowIdentifier 
:columnIdentifer 
to:aValue 
sender:sender

Notification that may be sent when the formatter has changed the value in a field.  The field that changed is identified by its rowIdentifier and its columnIdentifier (for the situation in which both rows and columns are static).

The argument aValue is the object that contains the new value.  The argument sender is the sender of the message (usually a formatter).  Returns self.

formatterDidChangeValueFor:at:sender:

- formatterDidChangeValueFor:identifier 
at:(unsigned int)position 
sender:sender

Notification that may be sent when the formatter has changed the value in a field.  The field that changed is identified by its identifier (usually associated with a column, but could be the identifier of a row if rows are static) and its position (usually a row number, but could be a column number if columns are dynamic).

The argument sender is the sender of the message (usually a formatter).  Returns self.

formatterDidChangeValueFor:at:to:sender:

- formatterDidChangeValueFor:identifier 
at:(unsigned int)position 
to:aValue 
sender:sender

Notification that may be sent when the formatter has changed the value in a field.  The field that changed is identified by its identifier (usually associated with a column, but could be the identifier of a row if rows are static) and its position (usually a row number, but could be a column number if columns are dynamic).

The argument aValue is the object that contains the new value.  The argument sender is the sender of the message (usually a formatter).  Returns self.

formatterWillChangeValueFor::to:sender:

- (BOOL)formatterWillChangeValueFor:rowIdentifier
:columnIdentifier 
to:aValue 
sender:sender

Notification that may be sent when the formatter is about to change the value in a field.  The field in which the proposed change will take place is identified by its rowIdentifier and its columnIdentifier (for the situation in which both rows and columns are static).

The argument aValue is the object that contains the proposed new value.  The argument sender is the sender of the message (usually a formatter).  Returning YES permits the change to be recorded in the record list (and thus ultimately in the database).

formatterWillChangeValueFor:at:to:sender:

- (BOOL)formatterWillChangeValueFor:identifier
at:(unsigned int)position 
to:aValue 
sender:sender

Notification that may be sent when the formatter is about to change the value in a field.  The field in which the proposed change will take place is identified by its identifier (usually associated with a column, but could be the identifier of a row if rows are static) and its position (usually a row number, but could be a column number if columns are dynamic).

The argument aValue is the object that contains the proposed new value.  The argument sender is the sender of the message (usually a formatter).  Returning YES permits the change to be recorded in the record list (and thus ultimately in the database).